Database application including spilt views

ABSTRACT

A database application is provided which includes functionality for providing split views. The database application includes an object model having a number of objects, methods, and properties. The object model preferably includes a form object which includes a split view representation. A number of properties are associated with the split view which provides for the presentation of data to a user of the database application.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of application Ser. No. 11/159,763filed Jun. 23, 2005, now U.S. Pat. No. 7,734,664, which is incorporatedherein by reference in its entirety.

BACKGROUND OF THE INVENTION

Current desktop database applications allow a user to manipulate data ina variety of ways. A desktop database application can be used toorganize and maintain data associated with the many differentapplications. For example, a desktop database application may be usedfor organizing and maintaining a construction project schedule. Asanother example, a desktop database application may be used fororganizing and maintaining personal or business contacts. Additionally,a desktop database application may be used to track inventory orders andshipping dates related to certain inventory. In these instances andothers, it is not unusual for a desktop database application to includelarge amounts of data. Consequently, a user can be overwhelmed and thusfrustrated when working with large amounts of data. There are occasionswhen a user would prefer to view a large amount of data while editingone or more portions of that data. For example, a user may want to viewmany records on a screen at one time while simultaneously viewing and/orediting details of a single record from the record set. Unfortunately,current desktop database applications do not provide such a mechanism.

It is with respect to these considerations and others that the variousembodiments of the present invention have been made.

SUMMARY OF THE INVENTION

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended asan aid in determining the scope of the claimed subject matter.

Exemplary embodiments of the present invention provide methods andcomputer-readable medium for providing a database application havingvarious views. The database application includes an object model havinga number of objects which provide programmatic access and implementvarious views to a user, including split views. In preferredembodiments, the object model includes a form object. The form objectpreferably includes a number of “visualizations” one of which is a splitview, which includes a number of properties and associated settings forpresenting data to a user of the database application. The split viewcan be utilized with any data schema and type.

The database application can be used to create tables, queries, forms,reports, etc. According to a preferred embodiment, the databaseapplication is a desktop database application and is operable to providedifferent split views which enable a user to view and/or modify avariety of data at a given time. According to the preferred embodiments,a user is able view and/or edit multiple records and record details at atime using split views of the database application. A user can configurethe split view according to user preference, using a user interface orother programming interface if desired. For example, a user, using thedatabase application, can configure the split view in horizontal andvertical orientations, and simultaneously view data as part of adatasheet and a form.

These and other features and advantages, which characterize the presentinvention, will be apparent from a reading of the following detaileddescription and a review of the associated drawings. It is to beunderstood that both the foregoing general description and the followingdetailed description are explanatory only and are not restrictive of theinvention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary computingenvironment for implementation of various embodiments of the presentinvention.

FIG. 2 depicts a block diagram of a database application and associatedobject model according to an embodiment of the invention.

FIGS. 3A-3B are screen shots from a database application illustratingaspects of the invention.

FIG. 4 is a screen shot from a database application illustrating aspectsof the invention.

FIG. 5 is a screen shot from a database application illustrating aspectsof the invention.

FIG. 6 is a screen shot from a database application illustrating aspectsof the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention provide methods andcomputer-readable medium for providing a database application havingvarious views. The database application includes an object model havinga number of objects, modes, and properties for providing various viewsto a user, including split views. In preferred embodiments, the objectmodel includes a form object. The form object preferably includes anumber of “visualizations”, one of which is a split view which includesa number of properties and associated settings for presenting data to auser of the database application. The split view can be utilized withany data schema and type. A visualization can be described as a way todisplay data. “Single-record forms” is another visualization whichdepict one record from the data set at a time. “Continuous forms” is avisualization which show many records at one time in a custom layout.“Datasheets” is another visualization which show many records at a timein a grid.

The database application can be used to create tables, queries, forms,reports, etc. According to preferred embodiments, the databaseapplication is operable to provide split views which enable a user tosimultaneously view and/or edit multiple records and record details.Using the database application, a user can view and edit a particularrecord in simultaneous views. A user can configure the split viewaccording to user preference, using a user interface or otherprogramming interface if desired. For example, a user, using thedatabase application, can configure the split view in horizontal andvertical orientations, and adjust the split view according topreference.

Exemplary Operating Environment

Referring now to the drawings, in which like numerals represent likeelements, various aspects of the present invention will be described. Inparticular, FIG. 1 and the corresponding discussion are intended toprovide a brief, general description of a suitable computing environmentin which embodiments of the invention may be implemented. While theinvention will be described in the general context of program modulesthat execute in conjunction with program modules that run on anoperating system on a personal computer, those skilled in the art willrecognize that the invention may also be implemented in combination withother types of computer systems and program modules.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Moreover, those skilled inthe art will appreciate that the invention may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like. Theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

Referring now to FIG. 1, an illustrative operating environment forembodiments of the invention will be described. As shown in FIG. 1,computer 2 comprises a general-purpose desktop, laptop, or other type ofcomputer capable of executing one or more application programs. Inparticular, according to the various embodiments of the invention, thecomputer 2 is operative to execute a database application 24. As knownto those skilled in the art, a database application program 24 providesfunctionality including, but not limited to, organizing, accessing, andsharing information. According to a preferred embodiment, the databaseapplication program includes an object model 25, described in detailbelow.

According to one preferred embodiment of the invention, a databaseapplication 24 comprises the ACCESS database application program, herebyincorporated by reference in its entirety, from MICROSOFT CORPORATION ofRedmond, Wash. After using the database application 24, the informationmay be saved to a data file 26 on the mass storage device 14. Additionaldetails regarding the operation of the ACCESS 2003 application programare publicly available from MICROSOFT CORPORATION of Redmond, Wash. Itshould be appreciated, however, that the various aspects of theinvention described herein may be utilized with other databaseapplications and other related programs from various manufacturers.

FIG. 1 depicts an illustrative computer architecture for a computer 2utilized in various embodiments of the invention. The computerarchitecture illustrates a conventional desktop, laptop, or othercomputer, including a central processing unit 8 (“CPU”), a system memory12, including a random access memory 18 (“RAM”) and a read-only memory(“ROM”) 20, and a system bus 10 that couples the memory to the CPU 8. Abasic input/output system containing the basic routines that help totransfer information between elements within the computer, such asduring startup, is stored in the ROM 20. The computer 2 further includesa mass storage device 14 for storing an operating system 32, applicationprograms, and other program modules, which will be described in greaterdetail below.

The mass storage device 14 is connected to the CPU 8 through a massstorage controller (not shown) connected to the bus 10. The mass storagedevice 14 and its associated computer-readable media providenon-volatile storage for the computer 2. Although the description ofcomputer-readable media contained herein refers to a mass storagedevice, such as a hard disk or CD-ROM drive, it should be appreciated bythose skilled in the art that computer-readable media can be anyavailable media that can be accessed or utilized by the computer 2.

By way of example, and not limitation, computer-readable media maycomprise computer storage media and communication media. Computerstorage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solidstate memory technology, CD-ROM, digital versatile disks (“DVD”), orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer 2.

According to various embodiments of the invention, the computer 2 mayoperate in a networked environment using logical connections to remotecomputers through a network 4, such as a local network or the Internetfor example. The computer 2 may connect to the network 4 through anetwork interface unit 16 connected to the bus 10. It should beappreciated that the network interface unit 16 may also be utilized toconnect to other types of networks and remote computer systems. Thecomputer 2 may also include an input/output controller 22 for receivingand processing input from a number of other devices, including akeyboard, mouse, etc. (not shown in FIG. 1). Similarly, an input/outputcontroller 22 may provide output to a display screen, a printer, orother type of output device.

As mentioned briefly above, a number of program modules and data filesmay be stored in the mass storage device 14 and RAM 18 of the computer2, including an operating system 32 suitable for controlling theoperation of a networked personal computer, such as the WINDOWS XPoperating system from MICROSOFT CORPORATION of Redmond, Wash. The massstorage device 14 and RAM 18 may also store one or more program modules.In particular, the mass storage device 14 and the RAM 18 may store adatabase application program 24, as described above, and otherapplication programs, such as a word processing application 28, aspreadsheet application 30, e-mail application 34, etc. As brieflydescribed above, the database application 24 can comprise an applicationprogram for organizing, accessing, and sharing information.

Referring now to FIG. 2, a block diagram depicts a database application200 in accordance with an embodiment of the invention. The databaseapplication 200 includes an object model 201 that can include a numberof different types of objects, as described below. Each object caninclude one or more methods and/or properties. The methods andproperties are used to control and/or provide various functions orfeatures for the database application 200. Furthermore, the methods andproperties can be accessed and utilized by a programming interface 203for further application.

For example, certain object methods and properties can be used todisplay data, to store and manage data (including data entry anddeletion), to provide programming functionality and/or respond toevents, such as, but not limited to, data modification like creating newrecords or changing existing records, or user interaction like movingkeyboard or mouse focus from one field to another. Typical events inMICROSOFT ACCESS include BeforeUpdate and AfterUpdate, OnCurrent,OnFormat, OnLoad, OnUnload, etc. A programming application, such asVISUAL BASIC from MICROSOFT CORPORATION, can be used to create, control,and manage the different types of objects, methods, and properties ofthe database application 200. While the programming interface 203 isshown as a separate application in FIG. 2, it will be appreciated thatthe programming interface 203 can be implemented as part of the databaseapplication 200.

As described above, the database application 200 preferably includes anobject model 201. The object model 201 provides an applicationprogramming interface 203 for using, creating, and controlling objects,methods, properties, and/or related structure resident in the databaseapplication 200. Code can be used to manipulate these features of thedatabase application 200.

In a preferred embodiment, the object model 201 includes, but is notlimited to, a table object 202, query object 204, form object 206, and areport object 208. The table object 202, query object 204, form object206, and the report object 208 each include one or more methods and/orproperties. According to this preferred embodiment, the form object 206includes “visualizations” which provide for viewing and manipulatingdata, forms, datasheets, and other information when using the databaseapplication 200. Preferably, “visualizations” of the form object 206include, but are not limited to, a design view 210, continuous form view212, datasheet view 214, single form view 216, and a split view 218.

In one embodiment, the split view 218 preferably contains within it arendering of a datasheet and a form. A user can select the split viewoption from a menu, icon, or other application command. For example, thesplit view can be enabled using a drop-down menu, tool bar, or someother user interface mechanism. A user who enables the split view 218can simultaneously view and manipulate a form and datasheet when usingthe database application 200. Once the split view 218 has been enabled,the user can adjustably locate the form and datasheet horizontally orvertically, resizing and manipulating the view according to the user'spreference, as described further below.

According to an embodiment of the invention, the object model 201 can beused to display a datasheet above or below a form. Or, the object model201 can be used to display a datasheet to the right or to the left of aform. As described below, a user, using a user interface of the databaseapplication 200, can also utilize a splitter bar provided by thedatabase application 200. The splitter bar operates to delineate aboundary between a datasheet and a form. A user, using a mouse or otherinput device, can manipulate the splitter bar to adjust the height orwidth of the form and/or the data sheet. As described below, the splitview can also be output to a printer for printing.

The table below illustrates an exemplary object model corresponding tothe split view 218. The exemplary object model for the split view 218includes a number of properties and associated settings for implementingand controlling the split view 218. Each property of the split view 218preferably includes one or more settings which provide various methodsfor viewing and manipulating data when using the split view 218 of thedatabase application 200. The exemplary object model can be implementedand manipulated using a programming interface such as VISUAL BASIC, orincluded as part of the functionality of database application 200.

Each property can be individually set either through the user interfaceor the object model in order to achieve a specific behavior or look forthe split view. For example, in order to turn a single form view into asplit form view, you would set the DefaultView property to “Split Form”.To further refine the split form, you could select a specific split formorientation (i.e. Split Form Orientation “Datasheet on Bottom”). Thiswould create a form as a split form with the datasheet on bottom. Eachof these properties can be set to create the required environment forthe developer of the database.

TABLE Property Name Setting Description Default View Split Form (5)Similar to continuous (DefaultView) forms, provides a different way todisplay the form. Split Form Datasheet On Top When Default View is SplitOrientation (Default) (0) Form, then the datasheet is displayed on topDatasheet On When Default View is Split Bottom (1) Form, then thedatasheet is displayed on bottom Datasheet on When Default View is SplitLeft (2) Form, then the datasheet is displayed on left Datasheet on WhenDefault View is Split Right (3) Form, then the datasheet is displayed onright Split Form Datasheet Allow Edits The datasheet for the split(SplitFormDatasheet (Default) (0) form allows edits (default) Readonly)Read Only (1) The datasheet for the split form is read only Split FormYes (Default) (True) Display the Split Form Splitter Bar splitter bar No(False) Don't display the Split Form splitter bar. Split Form PrintingForm Only (0) Sets the default to print a (SplitFormPrinting) singleForm Datasheet Only (1) Sets the default to print the datasheet onlyusing the code of regular datasheet printing Save Splitter Bar Yes(Default) (True) Splitter bar position Position persisted No (False)Splitter bar position not persisted.

As shown in the Table above, the exemplary object model enables thedatabase application 200 to provide various split views to a user. Asdescribed above, the split view 218 preferably depends from and is basedon the form object 206. The split view 218 can be viewed on a display,such as an LCD or other display device, and also output to an outputdevice, such as a printer. According to this embodiment, the firstproperty of the split view 218 shown in the Table is the “Default View”property. The Default View property can be used to provide a mechanismfor enabling the split view, to thereby simultaneously display a formand datasheet to a user when using the database application 200.

FIG. 3A depicts a database application 300, wherein a user, using theuser interface 301, has elected to use a split view to view data. Afirst viewing area 302 can be used to render a form, according to aparticular user selection. Fields can be added to and/or subtracted fromthe form and/or the datasheet. In design-in-browse mode, the datasheetis a valid drop zone when dragging fields from a field list, and canbehave like the regular datasheet automatically populating controls onthe form. Preferably, the maximum viewing area that a form can occupy onopen (before manual resizing using the splitter bar) is about 80%regardless of form size. Therefore in a 1024×768 screen, the form may becreated at a maximum of about 384 pixels high. If the form is largerthan that, a scroll bar is preferably rendered. Accordingly, the defaultminimum size of the datasheet is about 20% of available window viewingarea.

As shown in FIG. 3B, a user is viewing a form 306 and a datasheet 308while using split views of the database application 300. FIG. 3B depictsa split horizontal view. The dual rendering includes contact informationpertaining to a number of contacts. A splitter bar 310 can also berendered to divide the view, so that the user can adjust the split form306 and datasheet 308 views. As described below, the splitter bar 310can be made adjustable, allowing the user to adjust the size of therendered view. Accordingly, the user, using split views can now view alarge number of data entries, while also viewing specific informationrelated to a particular entry.

The second property of the split view 218 is the “Split FormOrientation” property. According to a preferred embodiment, the SplitForm Orientation property includes four settings which are availablewhen using the split view 218. The first setting of the Split FormOrientation property is configured to display the datasheet above theform (see the horizontal configuration of FIG. 3B). The second settingof the Split Form Orientation property is configured to display thedatasheet below the single form.

FIG. 4 depicts a split view 400 where an exemplary form 402 has beenrendered above an exemplary datasheet 404 in a horizontal configuration.A splitter bar 406 separates the form 402 and datasheet 404horizontally. The third setting of the Split Form Orientation propertyis configured to display the datasheet to the left of the form. Thefourth setting of the Split Form Orientation property is configured todisplay the datasheet to the right of the form. FIG. 5 depicts a splitview 500 where an exemplary form 502 has been rendered to the left of anexemplary datasheet 504 in a vertical configuration. A splitter bar 506is shown which vertically delineates a boundary between the form 502 anddatasheet 504.

The next property of the split view 218 is the “Split Form Datasheet”property. Preferably, the Split Form Datasheet property has twosettings. The first setting of the Split Form Datasheet property isconfigured to allow edits to be made to the data displayed in the splitview 218. The second setting of the Split Form Datasheet property isconfigured to not allow edits to be made to the data in the datasheetwhile using the split view 218. For example, when the first setting isimplemented, a user can directly edit data of a datasheet. If the secondsetting is implemented, the datasheet is “read-only”, meaning no editsare allowed to the data populating the datasheet.

Continuing to refer to the Table above, the next property is the “SplitForm Splitter Bar” property. Preferably, the Split Form Splitter Barproperty has two settings. The first setting of the Split Form SplitterBar property is configured to render a splitter bar between a form and adatasheet when using the split view 218. The second setting of the SplitForm Splitter Bar property is configured to not render the splitter barbetween a form and a datasheet when using the split view 218. Forexample, when the first setting is implemented, a splitter bar isrendered in a vertical or horizontal orientation, based on the SplitForm Orientation property setting. The objective of this property is toallow or disallow user resizing of the split forms.

The next property in the Table is the “Split Form Printing” property.According to a preferred embodiment, the Split Form Printing propertyhas two settings. The first setting of the Split Form Printing propertyis configured to print a single form when using the split view 218. Thesecond setting of the Split Form Printing property is configured toprint the datasheet only. For example, when the first setting isimplemented, the user is able to print a particular form that has beenrendered when using the split view 218. When the second setting isimplemented, the user is able to print a particular datasheet that hasbeen rendered when using the split view 218.

FIG. 6 depicts a page setup window 600. The database application, suchas database application 200, renders the page setup window 600 when auser selects a print option using the user interface when using thesplit view 218. As shown in FIG. 6, the page setup window 600 includes afirst radio button 602 which is associated with form printing. A usercan select the first radio button 602 when desirous of a printed form.The page setup window 600 includes a second radio button 604 associatedwith datasheet printing. A user can select the second radio button 604when desirous of a printed datasheet. Preferably, these options areavailable when viewing a split view.

The next property “Save Splitter Bar Position” preferably has twosettings which allow the position of the splitter bar to be persisted ornot. Thus, using this property, a user can save the splitter barlocation, so that the next time the user is using the split view 218,the splitter bar will be automatically rendered at the previously savedlocation. Preferably, the splitter bar can be used to adjust the size ofthe form, not the datasheet. Thus, when the size of the form is reduced,more rows are shown than were previously shown on the datasheet forexample. It is also preferred that the top row visible is anchored tothe top of the window it occupies, either the splitter bar or the windowduring resize. When the form is enlarged, fewer rows are shown than werepreviously shown on the datasheet. The splitter bar may be used toresize the datasheet space to relative non-existence.

Using the foregoing properties of the split view 218, a user or anotherapplication can implement split views when using database application200. Furthermore, the properties can be used to provide programmaticaccess for developing code to further utilize aspects of the databaseapplication 200. It will be appreciated that the database application200 can be implemented such that an object model is mapped to the userinterface which includes features for allowing a user of the databaseapplication 200 to implement the split view 218. Moreover, theproperties of the split view may be set in design mode using code or aproperty sheet. The property sheet allows mapping functionality forsetting various behaviors of objects, etc. Using the user interface, auser can control how the form and datasheet will be displayed when usingthe split view 218. The user can also rearrange the view while in splitview 218. Thus, when a user wishes to view data using split views, thedatabase application 200 can enable the selected view through a propertysheet, automatically or upon user input.

According to a preferred embodiment of the invention, when the splitview is implemented, a user can use the interface for multi-selectoperations. Moreover, a selected item in a datasheet can be used todetermine what is shown in the associated form. In the case ofmulti-select, preferably there will be a “selected record” for eithermulti-selecting rows or columns. It is also preferred that the form andthe datasheet are in synchronization with respect to one another,meaning that at all times the primary selection in the datasheet isrendered in the form view. Additionally the record displayed in the formview will be selected in the datasheet. Therefore, regardless of whatmechanism an end user navigates with, the recordset and cursor are inthe same place. This goes beyond simple record level navigation and thecell focus is also reflected in selection. Filter and sort propertiespreferably apply to both the datasheet and form when the split view isimplemented. The user interface can implement the split view from adrop-down menu, button, macro, or other user interface selectable by akeyboard, mouse, stylus, or other pointing or selecting interface. Itwill be appreciated that the particular interface for availing the splitview can be designed and/or implemented in a variety of ways, and theinvention is not intended to limited to any particular embodiments orexamples discussed herein.

It will be appreciated that objects associated with a databaseapplication and the view that the user chooses can be determined by theuser to address the specific data task that they are trying toaccomplish. Whether this means to allow for data entry, display singlepieces of information, or to display and edit complex pieces of data inmultiple views to make it easier to read and understood by the end user,etc. For example, setting some available properties on the same form canenforce a data integrity rule requiring all addresses to have a stateassociated therewith. As another example, if a user wants to updateaddresses in his/her customer list, the user might create one particulartype of view (like a single-record form). If the user wanted to see afull list of all customers, another view might be more appropriate (likea datasheet). The split view allows for a combination of bothsingle-record forms and datasheets.

It should be appreciated that various embodiments of the presentinvention can be implemented (1) as a sequence of computer implementedacts or program modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance requirements of the computing system implementing theinvention. Accordingly, logical operations including related algorithmscan be referred to variously as operations, structural devices, acts ormodules. It will be recognized by one skilled in the art that theseoperations, structural devices, acts and modules may be implemented insoftware, firmware, special purpose digital logic, and any combinationthereof without deviating from the spirit and scope of the presentinvention as recited within the claims set forth herein.

Although the invention has been described in connection with variousexemplary embodiments, those of ordinary skill in the art willunderstand that many modifications can be made thereto within the scopeof the claims that follow. Accordingly, it is not intended that thescope of the invention in any way be limited by the above description,but instead be determined entirely by reference to the claims thatfollow.

1. A method for presenting data of a database application, the methodcomprising: providing an application programming interface, theapplication programming interface comprising one or more methods fordisplaying a split view form, the split view form having one or morevisualizations for viewing and manipulating data in the databaseapplication, the application programming interface providing for using,creating, and controlling a plurality of objects and properties, and thesplit view form associated with data of the database application;mapping the split view form to a user interface rendering a split view;presenting in the user interface rendering the split view a propertiessetting interface for setting properties mapping functionality forsetting behavior associated with the split view; setting propertiesmapping functionality for setting behavior associated with the splitview to control a visual rendering of the split view on a displaydevice, wherein the split view further includes at least a first viewand a second view, wherein the first view is a visual layout view andthe second view is a datasheet view of the underlying data for thevisual layout view; synchronizing the visual layout view with theunderlying data of the datasheet view; and simultaneously displaying thedatasheet view and the visual layout view synchronized with theunderlying data of the datasheet view.
 2. The method of claim 1, whereinthe setting properties mapping functionality for setting behaviorassociated with the split view further comprises: configuring a firstproperty to control the orientation of the split view; configuring asecond property to control a presentation order for the rendering; andconfiguring a third property with a control for automatically selectingwhether to print the visual layout view or the datasheet view.
 3. Themethod of claim 1, wherein the setting properties mapping functionalityfor setting behavior associated with the split view further comprisesconfiguring a property to allow edits to the datasheet view based on anassociated edit setting.
 4. The method of claim 1, wherein the settingproperties mapping functionality for setting behavior associated withthe split view further comprises configuring a property for delineatinga boundary between a layout view and the datasheet view based on anassociated setting.
 5. The method of claim 1, wherein the settingproperties mapping functionality for setting behavior associated withthe split view further comprises configuring a property for selectingprint capabilities for printing when using the split view.
 6. A methodfor presenting data of a database application, the method comprising:providing an application programming interface, the applicationprogramming interface for using, creating, and controlling a pluralityof objects and properties, the application programming interface fordisplaying a split view form, the split view form having one or morevisualizations for viewing and manipulating data in the databaseapplication; mapping the split view form to a user interface rendering asplit view; presenting, in the user interface rendering the split view,a properties setting interface for setting properties mappingfunctionality for setting behavior associated with the split view;setting properties mapping functionality for setting behavior associatedwith the split view to control a visual rendering of the split view on adisplay device, wherein the split view further includes at least a firstview and a second view, wherein the first view is a visual layout viewand the second view is a datasheet view of the underlying data for thevisual layout view; synchronizing the visual layout view with theunderlying data of the datasheet view; and simultaneously displaying thedatasheet view and the visual layout view synchronized with theunderlying data of the datasheet view in the rendered split view.
 7. Themethod of claim 6, wherein the setting properties mapping functionalityfor setting behavior associated with the split view further comprises:configuring a first property to control the orientation of the splitview; configuring a second property to control a presentation order forthe rendering; and configuring a third property with a control forautomatically selecting whether to print the visual layout view or thedatasheet view.
 8. The method of claim 6, wherein the setting propertiesmapping functionality for setting behavior associated with the splitview further comprises configuring a property to allow edits to thedatasheet view based on an associated edit setting.
 9. The method ofclaim 6, wherein the setting properties mapping functionality forsetting behavior associated with the split view further comprisesconfiguring a property for delineating a boundary between a layout viewand the datasheet view based on an associated setting.
 10. The method ofclaim 6, wherein the setting properties mapping functionality forsetting behavior associated with the split view further comprisesconfiguring a property for selecting print capabilities for printingwhen using the split view.
 11. A system for presenting data of adatabase application, comprising: a storage device for storing data in adatabase application; an application programming interface, theapplication programming interface having one or more methods forrendering a split view form, the split view form having one or morevisualizations for viewing and manipulating data in the databaseapplication, the application programming interface providing for using,creating, and controlling a plurality of objects and properties and thesplit view form; a processor, coupled to the storage device, theprocessor mapping the split view form to a user interface rendering asplit view, presenting in the user interface rendering the split view aproperties setting interface for setting properties mappingfunctionality for setting behavior associated with the split view,receiving property settings for setting behavior associated with thesplit view to control a visual rendering of the split view on a displaydevice, wherein the split view further includes at least a first viewand a second view, wherein the first view is a visual layout view andthe second view is a datasheet view of the underlying data for thevisual layout view, the processor synchronizing the visual layout viewwith the underlying data of the datasheet view and simultaneouslydisplaying the datasheet view and the visual layout view synchronizedwith the underlying data of the datasheet view in the rendered splitview.
 12. The system of claim 11, wherein the processor configures afirst property to control the orientation of the split view, configuresa second property to control a presentation order for the rendering andconfigures a third property with a control for automatically selectingwhether to print the visual layout view or the datasheet view.
 13. Thesystem of claim 11, wherein the processor configures a property to allowedits to the datasheet view based on an associated edit setting.
 14. Thesystem of claim 11, wherein the processor configures a property fordelineating a boundary between a layout view and the datasheet viewbased on an associated setting.
 15. The system of claim 11, wherein theprocessor configures a property for selecting print capabilities forprinting when using the split view.